QRZ! Ham Radio 5/QRZ Ham Radio Callsign Database - Volume 5.iso/digests/tcp/940190.txt

Internet Message Format | 1994-11-13 | 16.7 KB

Date: Thu,  1 Sep 94 04:30:02 PDT
From: Advanced Amateur Radio Networking Group <[e-mail]>
Errors-To: [e-mail]
Reply-To: [e-mail]
Precedence: Bulk
Subject: TCP-Group Digest V94 #190
To: tcp-group-digest


TCP-Group Digest            Thu,  1 Sep 94       Volume 94 : Issue  190

Today's Topics:
                     IP address question (5 msgs)
                  Kantronics 9612 - results (2 msgs)
                                Mosaic
                              NOS Hooks
                      pk232 into KISS from nos?
                      running Linux kernel AX.25
                              subscribe
                      TCP-Group Digest V94 #189
                             unsubscribe

Send Replies or notes for publication to: <[e-mail]>.
Subscription requests to <[e-mail]>.
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the TCP-Group Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives".

We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party.  Your mileage may vary.  So there.
----------------------------------------------------------------------

Date: Wed, 31 Aug 94 15:13:31 mdt
From: [e-mail]
Subject: IP address question
To: [e-mail]

Here's a little question for those familiar with NOS:

Suppose I have a system at home running JNOS 1.10c, with these network
connections:
    1. a packet radio interface on COM1
    2. an ethernet interface
    3. a SLIP interface on COM2

How many IP addresses do I need in order for this system to function,
possibly with all three of the TCP/IP network connections listed
above being active at the same time?

I think the answer is three IP addresses, with #3 (the SLIP interface)
possibly being dynamically assigned by a SLIP server, if that is the type of
SLIP connection I establish.  I just wanted to verify this with other people.

So, in other words, I think systems need an IP address for each TCP/IP network
interface the system has.  Right?

Thanks,
Gary

------------------------------

Date: Wed, 31 Aug 1994 20:42:28 -0500
From: "Milton D. Miller II" <[e-mail]>
Subject: IP address question
To: [e-mail]

NOS, unlike most unix stacks, only requires ONE ip address for all ports.

However, to support routing, you will probably end up using different
IP subnets and therefore addresses on each port.   NOS decides which
interface to send on based on the routing table and doesn't enforce
subnets -- you just have to set up your routing table.

milton
--
Milton Miller  KB5TKF  [e-mail]

------------------------------

Date: Wed, 31 Aug 94 15:48:18 HST
From: Antonio Querubin <[e-mail]>
Subject: IP address question
To: [e-mail]

> Suppose I have a system at home running JNOS 1.10c, with these network
> connections:
>     1. a packet radio interface on COM1
>     2. an ethernet interface
>     3. a SLIP interface on COM2
>
> How many IP addresses do I need in order for this system to function,
> possibly with all three of the TCP/IP network connections listed
> above being active at the same time?
>
> I think the answer is three IP addresses, with #3 (the SLIP interface)
> possibly being dynamically assigned by a SLIP server, if that is the type of
> SLIP connection I establish.  I just wanted to verify this with other people.
>
> So, in other words, I think systems need an IP address for each TCP/IP network
> interface the system has.  Right?

Nope.  You need only one IP address for any single system.  As long as
you can specify explicitly the broadcast address for
non-point-to-point ports to match a sub-network's broadcast address you'll
be ok.  If you're running 3 ports then you're probably running as a
router between three nets.  RIP will send routing updates using the
broadcast address for a port.  A host receiving your RIP updates will
log your IP address in it's routing tables as a SEPARATE entry
regardless of whether your IP address is in the same subnet.  The
exception is when the receiving host has 'rip merge on' AND your
router's IP address happens to be in the same subnet (the route is
merged in with the subnet route).  The bottom line is that a host does
NOT have to use an IP address that falls within the address space of a
subnet.  You might think 'gee what use is subnetting then?' well -
subnetting reduces the size of your routing table.  Typically, few
hosts act as routers off a subnet so the number of entries in a
routing table for routes beyond the local subnet are no big deal.

The only major reason I can think of off the top of my head for requiring
explicitly separate IP addresses per port is if your router has to
identify itself as being on a particular network (for whatever
security reasons) when it's acting as an IP client.  The
AMPRnet/Internet encapsulation gateways come to mind for example.
Maybe some other folks on this group can come up with other reasons...

Tony

------------------------------

Date: Wed, 31 Aug 94 23:20 EDT
From: [e-mail] (Russell Nelson)
Subject: IP address question
To: [e-mail]

   Date: Wed, 31 Aug 1994 20:42:28 -0500
   From: "Milton D. Miller II" <[e-mail]>

   NOS, unlike most unix stacks, only requires ONE ip address for all ports.

   However, to support routing, you will probably end up using different
   IP subnets and therefore addresses on each port.   NOS decides which
   interface to send on based on the routing table and doesn't enforce
   subnets -- you just have to set up your routing table.

NOS does it right; Unix does it wrong.  There is no particular reason
to force a single subnet on a single interface.  Or rather, there is a
reason to do it, but also reasons not to do it.  I like to have the
choice.  Plus, it's just plain simpler to understand even if you *do*
put a single subnet on a single interface.

-russ <[e-mail]>    http://www.crynwr.com/crynwr/nelson.html
Crynwr Software   | Crynwr Software sells packet driver support | ask4 PGP key
11 Grant St.      | [phone] (9201 FAX)  | What is thee doing about it?
Potsdam, NY 13676 | LPF member - ask me about the harm software patents do.

------------------------------

Date: Thu, 01 Sep 1994 07:14:35 -0400
From: "Brandon S. Allbery" <[e-mail]>
Subject: IP address question
To: [e-mail]

In your message of Wed, 31 Aug 1994 23:20:00 EDT, you write:
+---------------
| NOS does it right; Unix does it wrong.  There is no particular reason
| to force a single subnet on a single interface.  Or rather, there is a
+------------->8

You might be interested to know that, not knowing any better, I set up the two
interfaces on my Linux box (kernel networking, not JNOS) with the same IP
address, and no distinct subnet on either interface --- and it seems to work
fine.

++Brandon
--
Brandon S. Allbery KF8NH     [44.70.4.88]          [e-mail]
Linux development:  iBCS2, JNOS, MH
Daily dreading Nehemiah Scudder^H^H^H^H^H^H^H^H^H^H^H^H^H^H^H^HRush Limbaugh

------------------------------

Date: Wed, 31 Aug 1994 07:52:11 -0500 (CST)
From: Bill Walker <[e-mail]>
Subject: Kantronics 9612 - results
To: [e-mail]

    Wow!  I kicked over an anthill with my question concerning
    the Kantronics 9612.  Seems there are lots of happy owners
    out there.

    The ability to operate two radios at once was mentioned
    several times, but everyone who mentioned it seemed just
    about to try it.

    Is the mechanism the same (i.e. set an 8th bit) as the KAM
    uses for dual port operations ?  If so, K5JB's NET will
    probably make the thing talk without modification.

    73 de Bill W5GFE

--
Bill Walker Ph.D.
Chairman, Dept. of Computer Science
East Central University
Ada, Oklahoma 74820-6899

e-mail:  [e-mail]
phone:   [phone] ext. 594
FAX:     [phone]

------------------------------

Date: Wed, 31 Aug 1994 16:35:37 +0100 (BST)
From: john <[e-mail]>
Subject: Kantronics 9612 - results
To: [e-mail] (Bill Walker)

>
>     Wow!  I kicked over an anthill with my question concerning
>     the Kantronics 9612.  Seems there are lots of happy owners
>     out there.
>
>     The ability to operate two radios at once was mentioned
>     several times, but everyone who mentioned it seemed just
>     about to try it.
>
>     Is the mechanism the same (i.e. set an 8th bit) as the KAM
>     uses for dual port operations ?  If so, K5JB's NET will
>     probably make the thing talk without modification.

Should be, the same goes for the DataEngine too. I have AmigaNOS talking to
both 1200 and 9600 ports together with exactly the same setup as used on my
KAM with the 300 and 1200 ports.

John
>
>     73 de Bill W5GFE
>
> --
> Bill Walker Ph.D.
> Chairman, Dept. of Computer Science
> East Central University
> Ada, Oklahoma 74820-6899
>
> e-mail:  [e-mail]
> phone:   [phone] ext. 594
> FAX:     [phone]
>

--
                 John Heaton   -   NRS Central Administrator
      MCC Network Unit, The University, Oxford Road, Manchester,  M13-9PL
            Phone: [phone]  -  FAX: [phone]

------------------------------

Date: Wed, 31 Aug 1994 12:55:40 -0600 (MDT)
From: Klarsen <[e-mail]>
Subject: Mosaic
To: TCP digest <[e-mail]>

    Well got mosaic working and connected to the World Wide Web (www)
servers. I did get Bdales paper on Mitrex mods. So here is how you do it:

    1. FTP to ftp.ncsa.uiuc.edu and log in with anaonymous (spelled
right) and your internet address as a password.

    2. Change directory to /Mosaic/Windows (and do use the cap M and W)

    3. D/L win32s.zip which is a modification to windows 3.1 that
makes it function as a 32 bit system.

    4. D/L wmos20a6r?.zip which is the mosaic software that is free.

    5. D/L winsock.zip which is Trumpet ver 1.0, a shareware program.

    6. D/L winapps.zip which has the telnet and ftp software for Trumpet.

    7. Quit and make a \mosaic and \trumpet directories and put
mosaic in it's dir. and put winapps and winsock in \trumpet.

    8. Make a \temp and put win32s there. Using pkzip ver 2.04g
pkunzip win32s. Read the readme and them pkunzip again. Then in windows
load the new windows software. It went fine the first time with me.

    9. Pkunzip mosaic and print out the documentation. Follow the
instructions and get mosaic.ini fixed up.

    10. Pkunzip the files in \trumpet and print out the documentation
and install Trumpet either for a packet driver to an ethernet connection
or use it to slip connect via the telephone.

    When you get all this done properly (it took me 4 hours) bring up
mosaic. You can from the first window go to Bdales web in Colorado very
fast and my HP laserjet series ll prints out almost everything I see on
the screen perfectly!

    If you don't have a 88386 or better cpu and run windows version
3.1 then ignore all above this line.

-karl k5di

------------------------------

Date: Thu, 1 Sep 94 9:39:05 EST
From: [e-mail] (c.small-acacia-ele-student-90064116)
Subject: NOS Hooks
To: [e-mail] (TCP-group relay)

G'day All,
  I have a decision to make.  I'm going to be looking at either modifying
or re-writing the RSPF code to make it work with v2.2.  Now it needs to use
some hooks, of course, to get information etc from other processes.

On my system at home, I have a Linux box and a NOS box.  At the moment the
NOS box has the radios, though I think soon I will be able to move them to
the Linux box.

My question, is there somewhere I can find the 'hooks' and calls for NOS?
I'd prefer to do my work in NOS as then I can easy compile versions for
other amateurs to test around here.  However I need some calls, which in
Unix are documented.

I have heard that some versions of NOS are a lot like Unix in their calls.
Is this just the newer versions of KarnCode or does this hold, for example,
jnos 1.10?

On a separate note, keep the list going.  I've learnt a lot and I'm sure
there is a lot of silent listeners out there reading.  This is, I think,
one of my first messages after reading it for 4 years.

  - Craig vk2xlz

--
//   /\     |    |   |  | |   ... Craig Small   [44.136.8.58] ... ...
||==|--|====|====|===|==|=|   ... INTERNET: [e-mail]
\\   \/     |    |   |  | |   ... AMPR    : VK2XLZ@VK2XSB ... ... ...

------------------------------

Date: Tue, 30 Aug 94 21:30:00 -0000
From: [e-mail] (Mike Bilow)
Subject: pk232 into KISS from nos?
To: [e-mail]

On 94 Aug 30 at 17:50, Charles Okstein wrote:

 CO> I'm just starting to use JNOS 1.10e.  I can't seem to get
 CO> my pk232 MBX into KISS mode and set the speed to 9600 from
 CO> the autoexec.nos file. Here's what I've tried based on
 CO> other's suggestions:

 CO> attach asy 0x3e8 5 ax25 ax3 2048 236 9600
 CO> param ax3 rts 1
 CO> param ax3 dtr 1
 CO> comm ax3 "FRack 4"
 CO> comm ax3 "HBaud 9600"
 CO> comm ax3 "KISS on"
 CO> comm ax3 "Restart"

 CO> JNOS works well otherwise when I put the Pk232 into KISS
 CO> via a windows program pc-packratt and then exit to JNOS.
 CO> Any ideas or suggestions?

Try sending CR characters in the "comm" statements:

comm ax3 "frack 4\r"
comm ax3 "hbaud 9600\r"
comm ax3 "kiss on\r"
comm ax3 "restart\r"

You should be able to do this in one line, in fact:

comm ax3 "\rfrack 4\rhbaud 9600\rkiss on\rrestart\r"

By the way, I don't think AEAs need the "restart" after "kiss on" like the
MFJs, but it can't hurt.

-- Mike


------------------------------

Date: Wed, 31 Aug 94 13:49 PDT
From: [e-mail] (Bruce Perens)
Subject: running Linux kernel AX.25
To: [e-mail]

A few people sent mail asking what versions of Linux I use to run
the kernel ax.25 .

First, I'd like you to note that part of the Linux networking software
was written by Fred Van Kempen, a Dutch CB-er who was thoroughly hassled
by various tcp-group posters for using packet-radio software that is
only intended for the Radio Amateur community. I'm glad Fred didn't
restrict _us_ from using _his_ software.

I am currently running Linux kernel version 1.1.48 . This can be downloaded
from ftp.funet.fi:pub/OS/Linux/PEOPLE/Linus/v1.1 . In that directory there
are tar files of complete systems, and patch files to bring the systems
up to the latest point revision.

The AX.25 software and much of the later Linux networking software comes
from Alan Cox GW4PTS. Alan's FTP site is sunacm.swan.ac.uk . In the
directory pub/Linux/Radio, you must download the files from AX25022,
AX25023, and AX25024. These contain tar files and diff files.

If building a Linux kernel is not your cup of tea, I will be
distributing a pre-built ham radio package for the Debian Linux
Distribution. Debian is a free, full-featured Linux system.
It's going to be about a month before that's ready. I'll announce
it here.

    Thanks

    Bruce Perens AB6YM

------------------------------

Date: Wed, 31 Aug 94 23:20:34 UTC
From: [e-mail]
Subject: subscribe
To: [e-mail]

I would like to subcribe tcp-group kb7zzs.ampr.org
Thankyou, Michael KB7ZZS

------------------------------

Date: Wed, 31 Aug 1994 09:57:54 -0800 (PDT)
From: [e-mail] (John Paul Morrison)
Subject: TCP-Group Digest V94 #189
To: [e-mail]

> Date: Tue, 30 Aug 94 10:55 EDT
> From: [e-mail] (Russell Nelson)
> Subject: Ajourn
> To: [e-mail]
>
> Definitely, let's keep up this technical dialogue.
>
> Has anyone else noticed that KA9Q beats the pants off commercial
> routers, e.g. the Livingston PortMaster?  Damn thing won't let me set
> up a static route to a network.  If I'd only run with my intuition and
> gotten a sync card with a packet driver, I'd have gotten the routing
> job done at half the cost AND half the time AND half the exasperation.

You've got to be kidding. I need to run KA9Q because it has an 'encap'
interface (tunneling IP over IP) for gateways, and I can easily hang a
KA9Q router.  For example, a wayward RPC program can go nuts sending
out udp packets to portmap on a machine on the other end, instant
sieze up of the NOS router. Or (so I'm told) run xmaze through a KA9Q
box that's routing to a 56kbps tcp/ip packet network, one or two mazes
get drawn and the NOS box dies. Maybe NOS just doesn't like UDP.

> -russ <[e-mail]>    http://www.crynwr.com/crynwr/nelson.html
> Crynwr Software   | Crynwr Software sells packet driver support | ask4 PGP key
> 11 Grant St.      | [phone] (9201 FAX)  | What is thee doing about it?
> Potsdam, NY 13676 | LPF member - ask me about the harm software patents do.

------------------------------

Date: Wed, 31 Aug 1994 10:50:19 -0400 (EDT)
From: Steve Houchins <[e-mail]>
Subject: unsubscribe
To: [e-mail]

unsubscribe [e-mail] tcp-group

------------------------------

End of TCP-Group Digest V94 #190
******************************